home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Network Supervisor's Toolkit
/
Network Supervisor's Toolkit.iso
/
novell
/
fyi8
/
080118.dos
< prev
next >
Wrap
Text File
|
1996-07-10
|
2KB
|
41 lines
Subject: VAPs and UPS Monitoring
Date: August 1, 1988
- - - - - - - - - - - - - - - - - - - - -
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!! NOTE: This problem has been fixed in later releases !!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
PROBLEM: A user reported that UPS monitoring did not operate properly
with the Btrieve VAP loaded. We have been told that the
keylock VAP was tested in Beta engineering. The same
behavior that the user reported was observed by the Beta
group.
Bottom line: UPS and VAPs don't get along right now.
Date: 3-Aug-88 6:43
We have tested v2.15 with UPS monitoring and have found the
following problems:
When a VAP is loaded and UPS monitoring is enabled, it does
not funtion properly. When power is removed from the UPS,
the attached workstations lock up and get abort retries.
They never get the message that the server is on auxiliary
power. When power is restored, the server begins to function
properly and the message "Commercial Power Restored" appears
at workstations attached.
SOLUTION: If VAPs are not present and UPS monitoring is enabled, it
functions as it should. When power is removed from the UPS,
the attached workstations continue running and receive the
broadcast that the server is on auxiliary power. When power
is restored, the server broadcasts commercial power has been
restored to the workstations attached.
The VAP that caused this problem in the field was the Btrieve
VAP. We used the keyboard LOCK VAP in our tests here and had
the same results. This tends to point to a problem in the
VAP interface and/or the UPS modules within the OS.